Method and apparatus for logging in an application

ABSTRACT

According to an example, a user device obtains a gesture track of a user and queries a gesture track database according to the gesture track obtained, wherein the gesture track database stores a relationship between the gesture track and account information of the user. The user device obtains the account information corresponding to the gesture track and provides the account information to a log-in server, so as to log in the application.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of International PatentApplication No. PCT/CN2013/080693, filed on Aug. 2, 2013, which claimsthe benefit of Chinese Patent Application No. 201210282434.6, filed onAug. 9, 2012, the disclosures of both of said applications being hereinincorporated by reference in their entirety.

FIELD

The present disclosure relates to computer techniques, and moreparticularly, to a method and an apparatus for logging in anapplication.

BACKGROUND

With the developments of computers, more and more applications may beinstalled in computers. In order to log in an application, a user needsto input account information, i.e., a user name and a password. Due tothe openness of the applications, most applications allow switching ofaccounts, i.e., for one application, a user may have multiple sets ofnames and passwords. When desiring to switch an account, the user inputsa new account he wants to use. This process requires frequent inputs andthe operation is complex. In addition, the keyboard input may leak theaccount of the user. The more times that the account is inputted, thehigher the risk becomes.

SUMMARY

According to an example of the present disclosure, acomputer-implemented method for logging in an application is provided.The method includes:

obtaining, by a user device, a gesture track of a user;

querying, by the user device, a gesture track database according to thegesture track obtained, wherein the gesture track database stores arelationship between the gesture track and account information of theuser;

obtaining, by the user device, the account information corresponding tothe gesture track; and

providing, by the user device, the account information to a log-inserver, so as to log in the application.

According to another example of the present disclosure, an apparatus forlogging in an application is provided. The apparatus includes:

a first gesture track obtaining module, configured to obtain a gesturetrack of a user;

a querying module, configured to query a gesture track databaseaccording to the gesture track obtained by the gesture track obtainingmodule, and to obtain account information corresponding to the gesturetrack if the gesture track database contains the gesture track;

a log-in module, configured to provide the account information obtainedby the querying module to a log-in server, so as to log in theapplication; and

the gesture track database, configured to save a relationship betweenthe gesture track and the account information.

According to still another example of the present disclosure, anon-transitory computer-readable storage medium comprising a set ofinstructions for logging in an application is provided, the set ofinstructions to direct at least one processor to perform acts of:

obtaining, by a user device, a gesture track of a user;

querying, by the user device, a gesture track database according to thegesture track obtained, wherein the gesture track database stores arelationship between the gesture track and account information of theuser;

obtaining, by the user device, the account information corresponding tothe gesture track; and

providing, by the user device, the account information to a log-inserver, so as to log in the application.

Other aspects or embodiments of the present disclosure can be understoodby those skilled in the art in light of the description, the claims, andthe drawings of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

Features of the present disclosure are illustrated by way of example andnot limited in the following figures, in which like numerals indicatelike elements, in which:

FIG. 1 is a schematic diagram illustrating an example of a user devicefor executing the method of the present disclosure.

FIG. 2 is a schematic diagram illustrating a method for establishing arelationship between gesture track and account information according toan example of the present disclosure.

FIG. 3 is a flowchart illustrating a first method for obtaining thegesture track of the user according to an example of the presentdisclosure.

FIG. 4 is a flowchart illustrating a second method for obtaining agesture track of the user according to an example of the presentdisclosure.

FIG. 5( a) and FIG. 5( b) are schematic diagrams showing two gesturetracks according to an example of the present disclosure.

FIG. 6 is a flowchart illustrating a method for logging in anapplication according to an example of the present disclosure.

FIG. 7 is a schematic diagram illustrating an apparatus 70 for loggingin an application according to an example of the present disclosure.

FIG. 8 is a schematic diagram illustrating a structure of the gesturetrack obtaining module 701 according to an example of the presentdisclosure.

FIG. 9 is a schematic diagram illustrating a structure of the gesturetrack obtaining module 701 according to another example of the presentdisclosure.

FIG. 10 is a schematic diagram illustrating an apparatus for logging inan application according to an example of the present disclosure.

DETAILED DESCRIPTION

The preset disclosure will be described in further detail hereinafterwith reference to accompanying drawings and examples to make thetechnical solution and merits therein clearer.

For simplicity and illustrative purposes, the present disclosure isdescribed by referring to examples. In the following description,numerous specific details are set forth in order to provide a thoroughunderstanding of the present disclosure. It will be readily apparenthowever, that the present disclosure may be practiced without limitationto these specific details. In other instances, some methods andstructures have not been described in detail so as not to unnecessarilyobscure the present disclosure. As used herein, the term “includes”means includes but not limited to, the term “including” means includingbut not limited to. The term “based on” means based at least in part on.In addition, the terms “a” and “an” are intended to denote at least oneof a particular element.

In various examples of the present disclosure, when the user desires tolog in an application or switch an account of the application, a gesturetrack of the user is obtained. A gesture track database which saves arelationship between the gesture track and account information of theuser is queried to obtain the account information corresponding to thegesture track. Then, the user device may transmit the accountinformation obtained to a log-in server for authentication. If theauthentication succeeds, the user successfully logs in the application.According to various examples of the present disclosure, the user isonly required to input the gesture track when desiring to log in theapplication or switch the account of the application. Compared withconventional systems, the user does not need to input the user name andthe password directly. Since the direct input of the account informationis avoided, the account information has a lower risk to be stolen andthe user's operation is simplified.

FIG. 1 is a schematic diagram illustrating an example of a user devicewhich may execute the method of the present disclosure. As shown in FIG.1, a user device 100 may be a computing device capable of executing amethod and apparatus of present disclosure. The user device 100 may, forexample, be a device such as a personal desktop computer or a portabledevice, such as a laptop computer, a tablet computer, a cellulartelephone, or a smart phone.

The user device 100 may vary in terms of capabilities or features.Claimed subject matter is intended to cover a wide range of potentialvariations. For example, the user device 100 may include akeypad/keyboard 156 and a mouse 157. It may also include a display 154,such as a liquid crystal display (LCD), or a display with a high degreeof functionality, such as a touch-sensitive color 2D or 3D display. Theuser device 100 may also include a camera 158.

The user device 100 may also include or may execute a variety ofoperating systems 141, including an operating system, such as a Windows™or Linux™, or a mobile operating system, such as iOS™, Android™, orWindows Mobile™. The user device 100 may include or may execute avariety of possible applications 142, such as a log-in application 145executable by a processor to implement the methods provided by thepresent disclosure.

Further, the user device 100 may include one or more non-transitoryprocessor-readable storage media 130 and one or more processors 122 incommunication with the non-transitory processor-readable storage media130. For example, the non-transitory processor-readable storage media130 may be a RAM memory, flash memory, ROM memory, EPROM memory, EEPROMmemory, registers, hard disk, a removable disk, a CD-ROM, or any otherform of non-transitory storage medium known in the art. The one or morenon-transitory processor-readable storage media 130 may store sets ofinstructions, or units and/or modules that comprise the sets ofinstructions, for conducting operations described in the presentapplication. The one or more processors may be configured to execute thesets of instructions and perform the operations in example embodimentsof the present application.

In various examples of the present disclosure, in order to enable theuser to log in the application using a gesture track, a relationshipbetween the gesture track and account information of the user needs tobe established in advance. The relationship may be stored in a gesturetrack database. Hereinafter, the establishment of the relationshipbetween the gesture track and the account information of the user willbe described in further detail.

FIG. 2 is a schematic diagram illustrating a method for establishing arelationship between the gesture track and the account informationaccording to an example of the present disclosure. FIG. 2 is asimplified diagram according to one embodiment of the present invention.This diagram is merely an example, which should not unduly limit thescope of the claims. One of ordinary skill in the art would recognizemany variations, alternatives, and modifications.

As shown in FIG. 2, the method includes the following processes.

At block 201, the user device 100 obtains account information of a user,wherein a relationship is to be established between the accountinformation and a gesture track.

In this block, the account information includes a user name and apassword of the user. When the user desires to establish therelationship between the account information and a gesture track, theuser inputs the account information first. In one example, the user mayinput the account information via the keypad/keyboard 156 or the mouse157 of the user device 100.

At block 202, the user device 100 obtains a gesture track of the user.

In this block, after inputting the account information, the user inputsa gesture track to be stored in association with the accountinformation. In the example as shown in FIG. 2, the user device 100obtains the account information of the user first, and then obtains thegesture track of the user. It should be noted that, in a practicalapplication, the user device 100 may also obtain the gesture trackfirst, and then obtain the account information of the user.

For different types of user devices 100, there may be different methodsto obtain the gesture track of the user.

For a portable user device 100 such as a smart phone, the gesture trackmay be obtained through capturing a slide movement of a user's finger ona touch screen of the portable user device 100.

For a fixed user device 100 such as a personal desktop computer, thegesture track may be obtained through capturing a handwriting track on atablet or through capturing a drag/drop action of the mouse 157 orthrough capturing a hand movement via the camera 158 of the user device100.

Hereinafter, the fixed user device is taken as an example user device100 to describe the obtaining of the gesture track of the user. Inparticular, the following two methods for obtaining the gesture track ofthe user by the fixed user device are described: (1) the gesture trackof the user is obtained according to a video stream captured by thecamera 158 of the user device 100; (2) the gesture track of the user isobtained according to mouse messages of the operating system 141 of theuser device 100.

It should be noted that, the present disclosure does not restrict thedetailed method for obtaining the gesture track of the user. Based onthe examples of the present disclosure, those ordinarily skilled in theart would obtain many variations without an inventive work.

FIG. 3 is a flowchart illustrating a first method for obtaining thegesture track of the user according to an example of the presentdisclosure. FIG. 3 is a simplified diagram according to one embodimentof the present invention. This diagram is merely an example, whichshould not unduly limit the scope of the claims. One of ordinary skillin the art would recognize many variations, alternatives, andmodifications.

In the method as shown in FIG. 3, the gesture track of the user isobtained according to a video stream captured by the camera 158 of thefixed user device 100. In particular, the process of obtaining thegesture track of the user includes the following operations.

At block 202-a, a video segment which includes a pre-determined numberof frames of images is obtained from the video stream captured by thecamera 158 of the user device 100.

In this example, before the video segment is obtained, the video streamcaptured by the camera 158 may be converted into a pre-determinedformat. Then, the video segment including the pre-determined number offrames of images is obtained from the video stream in the pre-determinedformat. Thus, the gesture track of the user may be obtained according topositions of a finger of the user in the frames of images.

At block 202-b, a position parameter of the finger of the user in eachframe of image is obtained according to a position of the finger in eachframe of image.

In this block, each frame of image may be divided into multiple zones,wherein each zone includes equal number of pixels. An identifier isassigned to each zone. Thus, the identifier of the zone where the fingerof the user is located may be taken as the position parameter of thefinger in the frame of image. Those with ordinary skill in the art mayalso obtain the position parameter of the finger of the user via othermanners. The present disclose does not restrict the detailed method forobtaining the position parameter.

In addition, if the finger of the user stretches over multiple zones,the position of a center point of the finger may be taken as areference, i.e., the position parameter corresponding to the centerpoint of the finger is taken as the position parameter of the finger inthe frame of image.

At block 202-c, it is determined whether the finger has moved accordingto position parameters of the finger in all frames of images. If thefinger has moved, block 202-d is performed. Otherwise, it is determinedthat the finger does not move. At this time, a message indicating thatthe gesture track of user is not obtained may be provided to user.

In this block, the process of determining whether the finger has movedmay include: determining whether the position parameter of the finger inframe (i−1) is the same with that in frame i, wherein i is an integersmaller than the pre-determined number of frames. If they are different,it is determined that the finger has moved.

If the position parameters of the finger in all frames of images are thesame, it is determined that the finger does not move. At this time, themethod may return to block 202-a to obtain a new video segment.

At block 202-d, a gesture track of the user is obtained. The gesturetrack takes the position of the finger in the first frame as a startpoint, takes the position of the finger in the last frame as an endpoint, and takes positions of the finger is other frames (i.e., framesexcept for the first frame and the last frame) as intermediate points.

Now, through the above blocks 202-a to 202-d, the gesture track of theuser is obtained. Hereinafter, the second method for obtaining thegesture track of the user will be described.

FIG. 4 is a flowchart illustrating a second method for obtaining agesture track of the user according to an example of the presentdisclosure. FIG. 4 is a simplified diagram according to one embodimentof the present invention. This diagram is merely an example, whichshould not unduly limit the scope of the claims. One of ordinary skillin the art would recognize many variations, alternatives, andmodifications.

In the method as shown in FIG. 4, the gesture track of the user isobtained according to mouse messages of the operating system 141 of thefixed user device 100. As shown in FIG. 4, the method includes thefollowing operations.

At block 202-A, mouse messages in the operating system 141 of the userdevice 100 are monitored.

Generally, with respect to different operations of the user, mousemessages include a left-button-down message, a left-button-up message, aleft-button-click message, a right-button-down message, aright-button-up message and a right-button-click message. Therefore,through monitoring the mouse messages in the operating system 141, theoperation of the user's mouse 157 may be determined. For example, theuser may press a right button of the mouse 157 and drag the mouse 157 todraw a triangle, and then release the right button of the mouse 157 tofinish the drawing of the triangle.

In the above procedure, the pressing of the right button and thereleasing of the right button respectively generates a right-button-downmessage and a right-button-up message. Therefore, through monitoring theright-button-down message and the right-button-up message, a movingtrack of the mouse (i.e., the gesture track of the user) may beobtained. Hereinafter, the right-button-down message and theright-button-up message are taken as an example to describe theobtaining of the gesture track according to the mouse messages in theoperating system 141. It should be noted that, those ordinarily skilledin the art may use other mouse messages to obtain the gesture track ofthe user, which is not restricted in the present disclosure.

At block 202-B, when detecting the right-button-down message, the userdevice 100 starts to record a moving track of the mouse 157. Whendetecting the right-button-up message, the user device 100 stopsrecording the moving track of the mouse 157.

At block 202-C, after the right-button-up message is detected, thegesture track of the user is obtained, wherein the moving track of themouse 157 recorded after the right-button-down message is detected andbefore the right-button-up message is detected is taken as the gesturetrack of the user.

Now, through the above blocks 202-A to 202-C, the gesture track of theuser is obtained through monitoring the mouse messages of the userdevice 100.

It should be noted that, in various examples of the present disclosure,for a closed gesture track such as a circle or a triangle, the user mayinput the gesture track in a clockwise direction or in a counterclockwise direction. For example, as shown in FIG. 5( a) and FIG. 5( b)which are schematic diagrams illustrating gesture tracks of the useraccording to an example of the present disclosure. It can be seen thatthe gesture tracks in FIG. 5( a) and FIG. 5( b) are both triangles,i.e., they have the same shape. However, the gesture track in FIG. 5( a)is in a clockwise direction (as shown by the arrows), whereas thegesture track is FIG. 5( b) is in a counter clockwise direction (asshown by the arrows).

According to a practical requirement, it is possible to consider merelythe shape of the gesture track but does not consider the direction ofthe gesture track. In other words, the gesture tracks as shown in FIG.5( a) and FIG. 5( b) are regarded as the same gesture track since theyhave the same shape. Alternatively, it is also possible to consider boththe shape and the direction of the gesture track. At this time, althoughtwo gesture tracks as shown in FIG. 5( a) and FIG. 5( b) have the sameshape, they are regarded as different gesture tracks since they havedifferent directions.

At block 203, a relationship is established between the gesture trackand the account information and is saved in a gesture track database.

The relationship may be stored in the gesture track database as a table,i.e., the gesture track and the account information are stored inassociation in the gesture track database acting as table items of thetable. In this block, in order to improve the security level of theaccount information of the user, the account information may beencrypted before being stored in the table.

It should be noted that, if the direction of the gesture track is takeninto consideration, both shape information and direction information ofthe gesture track are stored in the gesture track database.

Through the above blocks 201-203, the relationship has been establishedbetween the account information and the gesture track. Thus, the useronly needs to input the gesture track when desiring to log in theapplication or desiring to switch the account. In particular, the usermay input the gesture track via the mouse 157 or the camera 158 of theuser device 100 or through other manners. After the user device obtainsthe gesture track inputted by the user, the account informationcorresponding to the gesture track may be obtained according to therelationship saved in the gesture track database. Thus, the user isreleased from inputting the account information. Therefore, theoperation of the user is simplified. In addition, since the inputprocedure of the account information is avoided, the account informationhas a lower risk to be stolen.

In addition, after the gesture track of the user is obtained in block202, the method may further include a following process: determiningwhether the gesture track has been stored in the gesture track database.If the gesture track has been stored in the gesture track database, itindicates that the gesture track has been used, i.e., the gesture trackhas been stored in association with other account information. At thistime, a message indicating that the gesture track has been used may beprovided to the user. Then, the user may select another gesture trackand block 202 is repeated to obtain the new gesture track of the user.If the gesture track is not stored in the gesture track database, itindicates that the gesture track has not been used. Thus, a relationshipmay be established between this gesture track and the accountinformation of the user obtained in block 201.

In addition, if it is determined that the gesture track is not stored inthe gesture track database, the user may be required to input thegesture track again to ensure the correctness of the gesture track. Ifthe two gesture tracks are the same, the obtaining of the gesture tracksucceeds. Otherwise, a message indicating that the two gesture tracksare not consistent may be provided to the user. Then, the user may inputthe gesture track again.

Through the above blocks, the relationship between the gesture track andthe account information is established and saved in the gesture trackdatabase. Thereafter, the user is able to log in the application usingthe gesture track.

Hereinafter, the method for logging in an application through a gesturetrack will be described in further detail.

FIG. 6 is a flowchart illustrating a method for logging in anapplication according to an example of the present disclosure. FIG. 6 isa simplified diagram according to one embodiment of the presentinvention. This diagram is merely an example, which should not undulylimit the scope of the claims. One of ordinary skill in the art wouldrecognize many variations, alternatives, and modifications.

As shown in FIG. 6, the method includes the following operations.

At block 601, when a user desires to log in an application, the userdevice 100 obtains a gesture track inputted by the user.

Similarly to block 202, the gesture track of the user may be obtainedvia various methods. Detailed operations of this block are similar tothose in block 202 and will not be repeated herein.

At block 602, the gesture track database is queried according to thegesture track obtained in block 601.

At block 603, if the gesture track database contains the gesture trackobtained in block 601, account information corresponding to the gesturetrack is obtained.

In particular, the gesture track of the user is taken as an index tosearch the gesture track database. If the account informationcorresponding to the gesture track is found, the account information isobtained.

As described above, the gesture track has two features: (1) shape; and(2) direction. Therefore, when the gesture track database is queriedaccording to the gesture track of the user, there may be the followingtwo situations.

In a first situation, only the shape information of the gesture track isstored in the gesture track database. At this time, if the gesture trackof the user has the same shape with that stored in the gesture trackdatabase, it is determined that the gesture track database contains thegesture track of the user.

In a second situation, both the shape information and the directioninformation of the gesture track are stored in the gesture trackdatabase. At this time, if the gesture track of the user has both thesame shape and the same direction with that in the gesture trackdatabase, it is determined that the gesture track database contains thegesture track of the user.

In addition, if what is stored in the gesture track database isencrypted account information, after the account information is obtainedin this block, it is further required to decrypt the encrypted accountinformation to obtain decrypted account information.

Furthermore, if the gesture track database does not contain the gesturetrack obtained in block 601, a message indicating that the gesture trackinputted by the user is incorrect may be provided to the user. Then, theuser may input the gesture track again and the method returns to block601.

At block 604, the account information obtained in block 603 istransmitted to a log-in server which is responsible for authenticatingthe user according to the account information received. If theauthentication succeeds, the user logs in the application successfully;otherwise, a message indicating that the log-in fails may be provided tothe user.

According to the method provided by various examples of the presentdisclosure, the user is only required to input the gesture track whendesiring to log in an application. Compared with conventional systems,the input procedure of the account information is avoided. Thus, theaccount information has a lower risk to be stolen and the user'soperation is simplified.

In accordance with the above method, an example of the presentdisclosure further provides an apparatus for logging in an application.FIG. 7 is a schematic diagram illustrating an apparatus 70 for loggingin an application according to an example of the present disclosure.FIG. 7 is a simplified diagram according to one embodiment of thepresent invention. This diagram is merely an example, which should notunduly limit the scope of the claims. One of ordinary skill in the artwould recognize many variations, alternatives, and modifications.

As shown in FIG. 7, the apparatus 70 includes a gesture track obtainingmodule 701, a querying module 702, a log-in module 703 and a gesturetrack database 704.

The gesture track obtaining module 701 is configured to obtain a gesturetrack of a user.

The querying module 702 is configured to query the gesture trackdatabase 704 according to the gesture track obtained by the gesturetrack obtaining module 701, and to obtain account informationcorresponding to the gesture track if the gesture track database 704contains the gesture track.

In particular, the querying module 702 takes the gesture track obtainedby the gesture track obtaining module 701 as an index to query thegesture track database 704.

As described above, when the gesture track database 704 is queriedaccording to the gesture track obtained by the gesture track obtainingmodule 701, there may be the following two situations.

In a first situation, only the shape information of the gesture track isstored in the gesture track database 704. At this time, if the gesturetrack obtained by the gesture track obtaining module 701 has the sameshape with that stored in the gesture track database 704, it isdetermined that the gesture track database 704 contains the gesturetrack obtained by the gesture track obtaining module 701.

In a second situation, both the shape information and the directioninformation of the gesture track are stored in the gesture trackdatabase 704. At this time, if the gesture track obtained by the gesturetrack obtaining module 701 has both the same shape and the samedirection with that in the gesture track database 704, it is determinedthat the gesture track database 704 contains the gesture track obtainedby the gesture track obtaining module 701.

In addition, if what is stored in the gesture track database 704 isencrypted account information, after obtaining the account information,querying module 702 is further configured to decrypt the encryptedaccount information to obtain decrypted account information.

Furthermore, if the gesture track database 704 does not contain thegesture track obtained by the gesture track obtaining module 701, thequerying module is further configured to provide a message indicatingthat the gesture track inputted by the user is incorrect to the user.

The log-in module 703 is configured to transmit the account informationobtained by the querying module 702 to a log-in server which isresponsible for authenticating the user according to the accountinformation, wherein if the authentication succeeds, the user logs inthe application successfully.

The gesture track database 704 is configured to save a relationshipbetween the gesture track and the account information.

In particular, the gesture track obtaining module 701 may obtain thegesture track according to a video stream captured by a camera of theapparatus 70, or may obtain the gesture track according to mousemessages of an operating system of the apparatus 70, or through othermanners. It should be noted that the gesture track obtaining module 701may also obtain the gesture track via various manners, which is notrestricted in the present disclosure.

According to the apparatus 70 provided by various examples of thepresent disclosure, the user is only required to input the gesture trackwhen desiring to log in an application. Compared with conventionalsystems, the input procedure of the account information is avoided.Thus, the account information has a lower risk to be stolen and theuser's operation is simplified.

The above modules may be implemented by software (e.g. machine readableinstructions stored in the memory 130 and executable by the processor122 as shown in FIG. 1), hardware, or a combination thereof.

In addition, the above modules may be disposed in one or moreapparatuses. The above modules may be combined into one module ordivided into multiple sub-modules.

FIG. 8 is a schematic diagram illustrating a structure of the gesturetrack obtaining module 701 according to an example of the presentdisclosure. FIG. 8 is a simplified diagram according to one embodimentof the present invention. This diagram is merely an example, whichshould not unduly limit the scope of the claims. One of ordinary skillin the art would recognize many variations, alternatives, andmodifications.

As shown in FIG. 8, the gesture track obtaining module 701 includes:

a monitoring unit 801, configured to monitor mouse messages of anoperating system of the apparatus 70;

a gesture track recording unit 802, configured to start to record amoving track of a mouse of the apparatus 70 when a right-button-downmessage is detected, to stop recording the moving track of the mousewhen a right-button-up message is detected; and

a gesture track obtaining unit 803, configured to take the moving trackrecorded after the right-button-down message is detected and before theright-button-up message is detected as the gesture track of the user.

FIG. 9 is a schematic diagram illustrating a structure of the gesturetrack obtaining module 701 according to another example of the presentdisclosure. FIG. 9 is a simplified diagram according to one embodimentof the present invention. This diagram is merely an example, whichshould not unduly limit the scope of the claims. One of ordinary skillin the art would recognize many variations, alternatives, andmodifications.

As shown in FIG. 9, the gesture track obtaining module 701 includes:

a video segment obtaining unit 901, configured to obtain a video segmentincluding a pre-determined number of frames of images from a videostream captured by a camera of the apparatus 70;

a determining unit 902, configured to determine whether a finger of theuser moves according to position parameters of the finger in the framesof images; and

a gesture track obtaining unit 903, configured to obtain the gesturetrack of the user if the determining unit 902 determines that the fingerof the user moves, wherein the gesture track takes a position of thefinger in a first frame as a start point, takes a position of the fingerin a last frame as an end point, and takes positions of the finger inother frames as intermediate points.

FIG. 10 is a schematic diagram illustrating a structure of an apparatusaccording to an example of the present disclosure. As shown in FIG. 10,the apparatus includes: an account information obtaining module 1001, asecond gesture track obtaining module 1002, a relationship establishingmodule 1003, a first gesture track obtaining module 1004, a queryingmodule 702, a log-in module 703 and a gesture track database 704.

The functions of the first gesture track obtaining module 1004 aresimilar to those of the gesture track obtaining module 701 shown in FIG.7. The querying module 702, the log-in module 703 and the gesture trackdatabase 704 in FIG. 10 are respectively the same with correspondingmodules shown in FIG. 7. Therefore, the functions of these modules arenot repeated herein.

The account information obtaining module 1001 is configured to obtainaccount information inputted by the user and provide the accountinformation to the relationship establishing module 1003, wherein theaccount information includes a user name and a password of the user forlogging in the application.

The second gesture track obtaining module 1002 is configured to obtain agesture track inputted by the user and provide the gesture trackobtained to the relationship establishing module 1003. Detailedfunctions for obtaining the gesture track of the user may be seen fromthe above method examples and will not be repeated herein.

The relationship establishing module 1003 is configured to establish arelationship between the account information obtained by the accountinformation obtaining module 1001 and the gesture track obtained by thesecond gesture track obtaining module 1002, and is configured to providethe relationship to the gesture track database 704 for storage. Inparticular, the account information obtained by the account informationobtaining module 1001 and the gesture track obtained by the secondgesture track obtaining module 1002 may be saved in association witheach other in the gesture track database 704.

As described above, when providing the relationship to the gesture trackdatabase 704 for storage, the relationship establishing module 1003 mayprovide only the shape information of the gesture track obtained by thesecond gesture track obtaining module 1002 to the gesture track database704. Alternatively, the relationship establishing module 1003 may alsoprovide both the shape information and the direction information of thegesture track obtained by the second gesture track obtaining module 1002to the gesture track database 704.

In addition, in order to improve the security level of the accountinformation, the account information may be encrypted before beingstored in the gesture track database.

In one example, after obtaining the gesture track of the user, thesecond gesture track obtaining module 1002 is further configured todetermine whether the gesture track is stored in the gesture trackdatabase 704, provide a message indicating that the gesture track hasbeen used to the user if the gesture track is stored in the gesturetrack database 704, and provide the gesture track obtained to therelationship establishing module 1003 if otherwise.

In addition, after determining that the gesture track is not stored inthe gesture track database 704, the second gesture track obtainingmodule 1002 is further configured to obtain the gesture track for asecond time, compare whether two gesture tracks inputted by the user areconsistent, provide the gesture track to the relationship establishingmodule 1003 if the two gesture tracks are consistent, and provide amessage indicating that the two gesture tracks are inconsistent to theuser if otherwise.

What has been described and illustrated herein is a preferred example ofthe disclosure along with some of its variations. The terms,descriptions and figures used herein are set forth by way ofillustration only and are not meant as limitations. Many variations arepossible within the spirit and scope of the disclosure, which isintended to be defined by the following claims—and their equivalents—inwhich all terms are meant in their broadest reasonable sense unlessotherwise indicated.

What is claimed is:
 1. A computer-implemented method for logging in anapplication, comprising: obtaining, by a user device, a gesture track ofa user; querying, by the user device, a gesture track database accordingto the gesture track obtained, wherein the gesture track database storesa relationship between the gesture track and account information of theuser; obtaining, by the user device, the account informationcorresponding to the gesture track; and providing, by the user device,the account information to a log-in server, so as to log in theapplication; the method further comprising: before obtaining the gesturetrack of the user, establishing the relationship between the gesturetrack and the account information, and proving the relationship to thegesture track database for storage; wherein the establishing therelationship between the gesture track and the account information, andproviding the relationship to the gesture track database for storagecomprises: receiving, by the user device, the account informationinputted by the user; and obtaining, by the user device, the gesturetrack inputted by the user; and providing, by the user device, theaccount information and the gesture track to the gesture track databasefor storage, wherein the account information and the gesture track arestored in association with each other in the gesture track database;before providing the account information and the gesture track to thegesture track database, the method further comprising: determining, bythe user device, whether the gesture track database contains the gesturetrack inputted by the user; if the gesture track database does notcontain the gesture track inputted by the user, performing the processof providing the account information and the gesture track to thegesture track database.
 2. The computer-implemented method of claim 1,wherein the obtaining the gesture track of the user comprises: capturinga video stream via a camera of the user device, and obtaining thegesture track of the user according to the video stream captured; ormonitoring mouse messages of an operating system of the user device, andobtaining the gesture track of the user according to the mouse messages.3. The computer-implemented method of claim 2, wherein the obtaining thegesture track of the user according to the video stream capturedcomprises: obtaining, by the user device, a pre-determined number offrames of images from the video stream captured by the camera of theuser device; determining, by the user device, position parameters of afinger of the user in each frame of image according to positions of thefinger in each frame of image; determining, by the user device, whetherthe finger moves according to the position parameters of the finger inall frames of images; and obtaining, by the user device, the gesturetrack if it is determined that the finger moves, wherein a position ofthe finger in a first frame of image is taken as a start point of thegesture track, a position of the finger in a last frame of image istaken as an end point of the gesture track, and positions of the fingerin other frames of images are taken as intermediate points of thegesture track.
 4. The computer-implemented method of claim 2, whereinthe obtaining the gesture track of the user according to the mousemessages comprises: monitoring, by the user device, mouse messages ofthe operating system of the user device; if a right-button-down messageis detected, starting to record a moving track of a mouse of the userdevice; if a right-button-up message is detected, stopping recording themoving track of the mouse of the user device; and obtaining, by the userdevice, the gesture track of the user, wherein the moving track of themouse of the user device recorded after the right-button-down message isdetected and before the right-button-up message is detected is taken asthe gesture track of the user.
 5. The computer-implemented method ofclaim 1, further comprising: if the gesture track database contains thegesture track inputted by the user, providing, by the user device, amessage indicating that the gesture track has been used to the user. 6.The computer-implemented method of claim 1, wherein both shapeinformation and direction information of the gesture track are saved inthe gesture track database, or only shape information of the gesturetrack is saved in the gesture track database.
 7. An apparatus forlogging in an application, comprising: one or more processors; memory;and one or more program modules stored in the memory and to be executedby the one or more processors, the one or more program modulesincluding: a first gesture track obtaining module, configured to obtaina gesture track of a user; a querying module, configured to query agesture track database according to the gesture track obtained by thegesture track obtaining module, and to obtain account informationcorresponding to the gesture track if the gesture track databasecontains the gesture track; a log-in module, configured to provide theaccount information obtained by the querying module to a log-in server,so as to log in the application; and the gesture track database,configured to save a relationship between the gesture track and theaccount information; the apparatus further comprising: an accountobtaining module, a second gesture track obtaining module and arelationship establishing module; wherein the account obtaining moduleis configured to obtain the account information inputted by the user andprovide the account information to the relationship establishing module;the second gesture track obtaining module is configured to obtain thegesture track inputted by the user and provide the gesture trackobtained to the relationship establishing module; and the relationshipestablishing module is configured to establish a relationship betweenthe account information obtained by the account information obtainingmodule and the gesture track obtained by the second gesture trackobtaining module, and provide the relationship to the gesture trackdatabase for storage.
 8. The apparatus of claim 7, wherein the firstgesture track obtaining module further comprises: a monitoring unit,configured to monitor mouse messages of an operating system of theapparatus; a gesture track recording unit, configured to start to recorda moving track of a mouse when a right-button-down message is detected,to stop recording the moving track of the mouse when a right-button-upmessage is detected; and a gesture track obtaining unit, configured totake the moving track recorded after the right-button-down message isdetected and before the right-button-up message is detected as thegesture track of the user.
 9. The apparatus of claim 7, wherein thefirst gesture track obtaining module further comprises: a video segmentobtaining unit, configured to obtain a video segment including apre-determined number of frames of images from a video stream capturedby a camera of the apparatus; a determining unit, configured todetermine whether a finger of the user moves according to positionparameters of the finger in the frames of images; and a gesture trackobtaining unit, configured to obtain the gesture track of the user ifthe determining unit determines that the finger of the user moves,wherein the gesture track takes a position of the finger in a firstframe as a start point, takes a position of the finger in a last frameas an end point, and takes positions of the finger in other frames asintermediate points.
 10. The apparatus of claim 7, wherein therelationship establishing module is further configured to provide shapeinformation of the gesture track obtained by the second gesture trackobtaining module to the gesture track database; or provide both shapeinformation and direction information of the gesture track obtained bythe second gesture track obtaining module to the gesture track database.11. The apparatus of claim 7, wherein the second gesture track obtainingmodule is further configured to determine, after obtaining the gesturetrack of the user, whether the gesture track database contains thegesture track obtained by the second gesture track obtaining module,provide a message indicating that the gesture track has been used to theuser if the gesture track database contains the gesture track obtainedby the second gesture track obtaining module, and provide the gesturetrack obtained by the second gesture track obtaining module to therelationship establishing module if otherwise.
 12. The apparatus ofclaim 11, wherein the second gesture track obtaining module is furtherconfigured to receive, after determining that the gesture track databasedoes not contain the gesture track obtained by the second gesture trackobtaining module, the gesture track for a second time, compare whethertwo gesture tracks inputted by the user are consistent, provide thegesture track to the relationship establishing module if the two gesturetracks are consistent, and provide a message indicating that the twogesture tracks are inconsistent to the user if otherwise.
 13. Anon-transitory computer-readable storage medium comprising a set ofinstructions for logging in an application, the set of instructions todirect at least one processor to perform acts of: obtaining a gesturetrack of a user; querying a gesture track database according to thegesture track obtained, wherein the gesture track database stores arelationship between the gesture track and account information of theuser; obtaining the account information corresponding to the gesturetrack; and providing the account information to a log-in server, so asto log in the application; wherein before obtaining the gesture track ofthe user, receiving the account information inputted by the user; andobtaining the gesture track inputted by the user; and providing theaccount information and the gesture track to the gesture track databasefor storage; wherein before providing the account information and thegesture track to the gesture track database, determining whether thegesture track database contains the gesture track inputted by the user;if the gesture track database does not contain the gesture trackinputted by the user, performing the process of providing the accountinformation and the gesture track to the gesture track database.
 14. Thenon-transitory computer-readable storage medium of claim 13, wherein theprocess of obtaining the gesture track of the user comprises: capturinga video stream via a camera and obtaining the gesture track of the useraccording to the video stream captured; or monitoring mouse messages ofan operating system and obtaining the gesture track of the useraccording to the mouse messages.